Skip empty dag run conf rows and set statement timeout#50788
Conversation
e8eb093 to
5d34e0f
Compare
...low-core/src/airflow/migrations/versions/0055_3_0_0_remove_pickled_data_from_dagrun_table.py
Show resolved
Hide resolved
...low-core/src/airflow/migrations/versions/0055_3_0_0_remove_pickled_data_from_dagrun_table.py
Outdated
Show resolved
Hide resolved
airflow-core/src/airflow/migrations/versions/0049_3_0_0_remove_pickled_data_from_xcom_table.py
Show resolved
Hide resolved
ephraimbuddy
left a comment
There was a problem hiding this comment.
Should we create a new migration file instead of updating already released migrations? For new release, it would appear as if there's no migration on the version, and upgrading from a previous one like 3.0.1 won't run the migration.
I don't think so -- we're just optimizing the existing migrations. We've done this many times before. If a user is on 3.0.1, they've already passed the problematic migrations. So it remains true that there is no migration between 3.0.1 and 3.0.2. |
89fd264 to
a6e6afb
Compare
Also, set the statement timeout a little higher for xcom migration.
…_pickled_data_from_xcom_table.py Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
a6e6afb to
6b6f3a7
Compare
Backport failed to create: v3-0-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker f75b607 v3-0-testThis should apply the commit to the v3-0-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
Don't bother depickling `{}` object in dag run conf
Also, set the statement timeout a little higher for xcom migration.
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
Don't bother depickling `{}` object in dag run conf
Also, set the statement timeout a little higher for xcom migration.
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
Don't bother depickling `{}` object in dag run conf
Also, set the statement timeout a little higher for xcom migration.
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
(cherry picked from commit f75b607)
…pache#50788) Don't bother depickling `{}` object in dag run conf Also, set the statement timeout a little higher for xcom migration. Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com> (cherry picked from commit f75b607)
Don't bother depickling
{}object in dag run confAlso, set the statement timeout a little higher for xcom migration.